System and method for representing mfs control blocks in xml for mfs-based ims applications

ABSTRACT

A system and method for representing MFS control blocks in XML for MFS-based IMS applications utilizes an MFS XML adapter and an MFS XML repository to translate between XML and MFS. The repository contains XML files for DOF/MOD and XML files for DIF/MID. When an XML request is received, the XML request is transformed to a byte stream by retrieving the relevant information from the MFS XML repository. The byte stream can then be placed in an IMS message queue to await processing by an MFS-based IMS application program. A byte stream response is generated by the MFS-based IMS application and is transformed into an XML response, again, by retrieving the relevant information from the MFS XML repository.

FIELD OF THE INVENTION

The present invention relates generally to computer software, and morespecifically to IMS software.

BACKGROUND OF THE INVENTION

By some estimates, nearly seventy percent (70%) of corporate data in theUnited States and abroad resides on mainframe computers, e.g., S/390mainframes manufactured by International Business Machines. Moreover,business-to-business (B2B) e-commerce is expected to grow at least fivetimes faster than the rate of business-to-consumer (B2C) e-commerce.Many transactions involving this corporate data can be initiated byWindows/NT servers, UNIX servers, and other servers but the transactionsmust be completed on the mainframe using existing legacy applicationsresiding thereon.

One very crucial group of legacy applications are the message formatservice-based information management system applications (“MFS-based IMSapplications”) on which many businesses depend heavily. MFS is afacility of the IMS transaction management environment that formatsmessages to and from many different types of terminal devices. Asbusinesses upgrade their technologies to exploit new B2B technologies,there is a requirement for an easy and effective method for upgradingexisting MFS applications to include e-business capabilities. One suche-business capability is the ability to send and receive MFS-based IMStransaction messages as extensible markup language (XML) documents.

The MFS language utility compiles MFS source code, generates MFS controlblocks in a proprietary format and uses the control blocks to indicateto an IMS application how input and output messages are formatted. Forinput messages, MFS control blocks define how a message that is to besent by a device or remote program is mapped to an application program'sinput/output (I/O) area. For output messages, MFS control blocks definehow the message to be sent by the application program is mapped to thedevice's screen or the remote program. The MFS control blocks arecompiled off line from the MFS source files and are stored in the hostformat library by the MFS language utility.

Currently, there are four types of MFS control blocks that are used tomap input and output messages between an MFS-based application programand a displayable device or remote program. Message Output Descriptors(MODs) describe the layout of the output messages that are received froman MFS-based application program. Device Output Formats (DOFs) describedhow MFS on-line processing formats output messages for each of thedevices or remote programs with which the application communicates.Device Input Formats (DIFs) describe the formats of input messages thatMFS on-line processing receives from each of the devices or remoteprograms with which the application communicates. Message InputDescriptors (MIDs) described how MFS on-line processing further formatsinput messages so that the application program can process them.

As business processes are updated to exploit new B2B technologies, thereis a requirement to support B2B interchanges. However, MFS controlblocks are presently coded in an IBM proprietary language format andthere does not exist any way to represent MFS control blocks in XML toformat XML input and output messages between MFS-based IMS applicationsand displayable devices, e.g., PDA or Web browsers, or remote programs.Also, it is currently problematic to save and load XML files without theexistence of external references.

A non-proprietary, industry-wide standard method is needed to representthe information in today's MFS control blocks. It happens that XML isgrowing in acceptance as the universal data format which can be theinput and output for any application. If the MFS control blocks arerepresented in XML, they can easily be used for developing new softwareto map XML messages for IMS MFS transaction applications. Using MFScontrol blocks in XML can encourage a wide range of connection types andtools to be developed and provide a simple and unified way to re-useexisting MFS-based IMS transaction applications.

Accordingly, there is a need for a system and method for representingMFS control blocks in an industry-wide standard format. Moreover, thereis a need for a system and method for allowing references to externalXML files containing MFS control blocks from within a given XML filewithout having the external XML files present and/or created.

SUMMARY OF THE INVENTION

A method for representing MFS control blocks in XML for MFS-based IMSapplications includes establishing an MFS XML repository. Plural XMLfiles representing plural MFS control blocks are stored in the MFS XMLrepository. Preferably, an XML request is transformed into a byte streamrequest based on the XML files within the MFS XML repository. The bytestream request can be processed by an MFS-based IMS application programto yield a byte stream response. Again, based on the XML files withinthe repository, the byte stream response is transformed into an XMLresponse.

In a preferred embodiment, a first MFS source file is parsed and it isdetermined whether an unresolved external reference is encountered whileparsing the first MFS source file. Based on the determination, askeleton XML file for an externally reference control block is created.The skeleton XML file can include a present file name in the externalcontrol block name. Further, in a preferred embodiment, a second MFSsource file is parsed and it is determined whether a previouslyencountered externally referenced control block is again encounteredwhile parsing the second MFS source file. Based on the determination, apreviously created skeleton XML file can be populated with informationfrom the control block.

In another aspect of the preferred embodiment of the present invention,a system for representing MFS control blocks in XML for MFS-based IMSapplications includes an MFS XML adapter and an MFS XML repositoryconnected thereto. The MFS XML repository includes plural XML files thatrepresent plural MFS control blocks. The system further includes acomputer program for representing MFS control blocks in XML forMFS-based IMS applications. In this aspect, the computer programincludes logic means that can transform an XML request into a bytestream request based on the XML files in the MFS XML repository.

In yet another aspect of the preferred embodiment of the presentinvention, a computer program device for representing MFS control blocksin XML for MFS-based IMS applications includes logic means for receivingan XML request and logic means for transforming the XML request into abyte stream. Further, the computer program device includes logic meansfor placing the byte stream request in an IMS message queue.

The preferred embodiment of the present invention will now be described,by way of example, with reference to the accompanying drawings, inwhich:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram representing the present invention;

FIG. 2 is a flow chart of the overall logic of the present invention;and

FIG. 3 is a flow chart of the MFS source file parsing logic.

DESCRIPTION OF AN EMBODIMENT OF THE INVENTION

Referring initially to FIG. 1, a block diagram of the system forfacilitating XML transactions with MFS-based IMS applications is shownand is generally designated 10. FIG. 1 shows that the system 10 includesa user computer 11 connected, e.g., via the Internet to a first server12. Within the first processor 12, is an MFS XML adapter 14 thatcommunicates with MFS XML control blocks 16 that are retrieved from anMFS XML repository 18. In a preferred embodiment, the MFS XML adapter 14is the software-implemented MFS XML adapter that is executed within thefirst processor 12 and that is discussed in U.S. patent application Ser.No. 10/244,722, incorporated herein by reference. It is to be understoodthat the MFS XML adapter 14 includes a mapper which maps the XMLdocument pertaining to the device information into the appropriate MFSXML messages (and vice versa). Also, the MFS XML adapter 14 includes aconverter that transforms the MFS XML messages into a byte stream andvice versa. The MFS importer reads and parses MFS source files for aparticular application and generates XML files that describe theMFS-based application interface using the MFS Metamodel discussed inU.S. patent application Ser. No. 09/849,105, incorporated herein byreference, which is part of the Common Application Metamodel (CAM)disclosed in U.S. Provisional Application Ser. No. 60/223,671, alsoincorporated herein by reference.

FIG. 1 shows that the MFS XML adapter 14 communicates with an IMSmessage queue 20 which, in turn, communicates with a second server 22that hosts an MFS-based IMS application program 24. An MFS-based IMSapplication program 22 can, e.g., be a program for tracking inventory.Further, as shown in FIG. 1 and stated above, the MFS XML adapter 14communicates with the MFS XML repository 18 in order to retrieve thenecessary XML control blocks 16 for message formatting. Preferably, afirst XML control block for DOF/MOD 26, an XML control block for DIF/MID28, and a second XML control block for DOF/MOD 30 are retrieved from theMFS XML repository 18. Moreover, as described in detail below, the MFSXML adapter 14 provides a request for MFS format 32 to the MFS XMLrepository 18. The MFS adapter 14 retrieves an MFS format 34 from theMFS XML repository 18 and later returns the output 36.

It can be appreciated that the present invention groups MID and DIFfiles together as one XML control block and groups MOD and DOF filestogether as another control block. These groupings reduce the load timeof XML files during execution. Moreover, the generated XML files for MFScontrol blocks can be stored in the MFS XML repository 18, as describedabove. Unlike the existing MFS format library, which must be closelycoupled to the host processor where the MFS-based IMS application 24resides, the MFS XML repository 18 containing the MFS control blocks inXML does not have to be tied to the same host processor in which theMFS-based IMS application 24 resides. The MFS XML repository 18 canreside in any processor, including a Windows-based processor, in whichthe MFS XML Adapter 14 resides. A local file system, or a databaserepository, e.g., DB2's XML repository, or an z/OS partitioned data setcan be used as the MFS XML repository 18.

It is to be understood that in the system 10 described above, the logicof the present invention can be contained on a data storage device witha computer readable medium, such as a computer diskette. Or, theinstructions may be stored on a magnetic tape, hard disk drive,electronic read-only memory (ROM), optical storage device, or otherappropriate data storage device or transmitting device thereby making acomputer program product, i.e., an article of manufacture according tothe invention. In an illustrative embodiment of the invention, thecomputer-executable instructions may be lines of C++ compatible code.

The flow charts herein illustrate the structure of the logic of thepresent invention as embodied in computer program software. Thoseskilled in the art will appreciate that the flow charts illustrate thestructures of computer program code elements including logic circuits onan integrated circuit, that function according to this invention.Manifestly, the invention is practiced in its essential embodiment by amachine component that renders the program elements in a form thatinstructs a digital processing apparatus (that is, a computer) toperform a sequence of function steps corresponding to those shown.

Referring now to FIG. 2, the overall logic of the present invention isshown and commences at block 50 wherein an XML request is received,e.g., at the MFS XML adapter 14 (FIG. 1), from the user computer 11. Atblock 52, the XML request is transformed to a byte stream by using theXML control blocks 16 retrieved from the MFS XML repository 18 (FIG. 1).It is to be understood that in an exemplary, non-limiting embodiment theXML request is transformed as follows: a request for MFS format 32 (FIG.1), in XML, is submitted by the MFS XML adapter 14 to the MFS XMLrepository 18 (FIG. 1). An XML control block for DOF/MOD 26 (FIG. 1) isretrieved to generate the MFS format 34 (FIG. 1) in XML. To complete therequest, data is input to the MFS format 34 (FIG. 1) and the completerequest is processed by the MFS XML adapter 14 (FIG. 1), again, in XML.An XML control block for DIF/MID 28 (FIG. 1) is used to format the XMLrequest with the proper input format to yield a byte stream message.

Moving to block 54, the byte stream is placed in the IMS message queue20 (FIG. 1). At block 56, the byte stream is processed by the MFS-basedIMS application program 24 (FIG. 1) to yield a byte stream response.Continuing to block 58, the byte steam response is queued to the IMSmessage queue 20 (FIG. 1). Next, at block 60, the byte stream responseis transformed into an XML response by retrieving the control blocksfrom of the MFS XML repository 18 (FIG. 1). For example, the byte streamrequest is returned to the MFS XML adapter 14 (FIG. 1) where an XMLcontrol block for DOF/MOD 30 (FIG. 1) is used to determine the format ofbyte stream request in order to generate an XML response message.Returning to the description of the logic, the XML response message isreturned, e.g., to the MFS XML adapter 14 (FIG. 1) and then the usercomputer 11. The logic then ends at state 64.

It is to be understood that XML files containing MFS control blocksrepresent all of the application interface information encapsulated bythe MFS source—including the input and output messages, displayinformation, MFS flow control, device characteristics and operationsemantics. From these types of XML files, the MFS XML adapter 14(FIG. 1) maps XML messages into the proper format for MFS-based IMSapplications. Thus, MFS-based IMS applications can be retargeted tosupport B2B XML communications without changing the IMS transactionitself. Additionally, a variety of displayable devices not yet supportedby MFS, including web browsers, can be supported.

Another aspect of the present invention is to reference non-existentinformation across different MFS source files. When an MFS control blockis represented as an XML file, a forward reference problem occurs ingenerating XML for these control blocks because XML files, when loadedor saved, require external references to exist. However, this is notalways possible or convenient. For example, when generating an XML filecontaining a MID control block from an MFS source file, the MIDstatement often has a reference to a MOD defined in another MFS sourcefile. The external reference to the MOD must be recorded. However, thisis not possible within XML unless this external reference alreadyexists, which would require creating an XML file out of the external MODbefore creating an XML file out of the MID. In the case in which anexternal MOD points to a MID which, in turn, points back to the originalMOD, the XML file containing the control blocks cannot be generatedbecause of the circular condition.

One possible solution to solve this forward reference problem in XML isto combine all original MFS sources into one large file for XMLcreation. Unfortunately, since most companies often have thousands ofMFS source files, this is not feasible. Also, if one MFS file ischanged, it requires regeneration of all XML files for all of thecontrol blocks.

Referring to FIG. 3, the MFS source file parsing logic, including thesolution to the above-mentioned forward reference problem, is shown andcommences at block 100. At block 100, MFS source files are parsed.Moving to decision diamond, it is determined whether an unresolvedexternal reference has been encountered. If not, the logic moves todecision diamond 104 where it is determined whether the final MFS sourcefile has been parsed. If the final MFS source file has been parsed, thelogic ends at state 106. Otherwise, the logic returns to block 100 andcontinues as described above.

Returning to decision diamond 102, if an unresolved external referencehas been encountered, the logic moves to block 108 where a skeleton XMLfile is created for the externally referenced control block with thepresent XML file's name in the external control block name. Thereafter,at block 110 the parsing of MFS source files continues. Proceeding todecision diamond 112, it is determined whether the same externallyreferenced control block has been encountered when parsing another MFSsource file. If not, the logic moves to decision diamond 104 andcontinues as described above. Otherwise, the logic continues to block114, where the previously created skeleton XML file is populated withactual information from the control block, and no changes are necessaryto the flies which referenced them. The logic then moves to decisiondiamond 104 and continues as described above.

It can be appreciated that this invention satisfies the externalreferences in an given XML file by generating skeleton XML files asplace holders with the appropriate filenames and empty top-level entity.Therefore, reloading existing XML files to check if they have potentialreferences to newly generated XML files is not required.

With the configuration of structure described above, it is to beappreciated that system and method described above provides a means forrepresenting MFS control blocks in an industry-wide standard format.Moreover, it provides a system and method for allowing references toexternal XML files containing MFS control blocks from within a given XMLfile without having the external XML files present and/or created.

While the particular SYSTEM AND METHOD FOR REPRESENTING MFS CONTROLBLOCKS IN XML FOR MFS-BASED IMS APPLICATIONS as herein shown anddescribed in detail is fully capable of attaining the above-describedaspects of the invention, it is to be understood that it is thepresently preferred embodiment of the present invention and thus, isrepresentative of the subject matter which is broadly contemplated bythe present invention, that the scope of the present invention fullyencompasses other embodiments which may become obvious to those skilledin the art, and that the scope of the present invention is accordinglyto be limited by nothing other than the appended claims, in whichreference to an element in the singular is not intended to mean “one andonly one” unless explicitly so stated, but rather “one or more.” Allstructural and functional equivalents to the elements of theabove-described preferred embodiment that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the presentclaims. Moreover, it is not necessary for a device or method to addresseach and every problem sought to be solved by the present invention, forit is to be encompassed by the present claims. Furthermore, no element,component, or method step in the present disclosure is intended to bededicated to the public regardless of whether the element, component, ormethod step is explicitly recited in the claims. No claim element hereinis to be construed under the provisions of 35 U.S.C. section 112, sixthparagraph, unless the element is expressly recited using the phrase“means for.”

1-8. (canceled)
 9. A system for representing MFS control blocks in XMLfor MFS-based IMS applications, comprising: an MFS XML adapter; an MFSXML repository connected to the MFS XML adapter, the MFS XML repositoryincluding at least one XML file representing at least one MFS controlblock; a computer program for representing MFS control blocks in XML forMFS-based IMS applications, the computer program comprising: logic meansfor transforming an XML request into a byte stream request at leastpartially based on the MFS control block within the MFS XML repository;wherein the XML file is at least one of the following: an XML file fordevice output format/message output descriptors (DOF/MOD) and an XMLfile for device input format/message input descriptors (DIF/MID), andwherein the computer program further comprises: logic means forprocessing the byte stream request with an MFS-based IMS applicationprogram to yield a byte stream response; logic means for transformingthe byte stream response into an XML response at least partially basedon the files in the MFS XML repository; logic means for parsing an firstMFS source file; and logic means for determining whether an unresolvedexternal reference is encountered while parsing the first MFS sourcefile. 10-15. (canceled)
 16. The system of claim 9, wherein the computerprogram further comprises: logic means for parsing a second MFS sourcefile; and logic means for determining whether a previously encounteredexternally referenced control block is again encountered while parsingthe second MFS source file.
 17. (canceled) 18-22. (canceled)
 23. Acomputer program device for representing MFS control blocks in XML forMFS-based IMS applications, comprising: logic means for establishing anMFS XML repository having at least one XML file representing at leastone MFS control block; logic means for transforming an XML request intoa byte stream request at least partially based on the XML file; logicmeans for parsing a first MFS source file; and logic means fordetermining whether an unresolved external reference is encounteredwhile parsing the first MFS source file. 24-28. (canceled)